Ultra-low latency phy/mac design for ieee 802.11

ABSTRACT

Provided herein is ultra-low latency (ULL) PHY/MAC design for IEEE 802.11. The disclosure provides an apparatus, comprising: interface circuitry; and processor circuitry coupled with the interface circuitry, wherein the processor circuitry is to: encode a ULL packet; and cause transmission of the ULL packet to an Access Point (AP) via the interface circuitry in an unlicensed spectrum, wherein a duration of the ULL packet is less than 20 microseconds. Other embodiments may also be disclosed and claimed.

TECHNICAL FIELD

Embodiments of the present disclosure generally relate to wireless communication, and in particular, to ultra-low latency (ULL) physical layer (PHY)/medium access control (MAC) design for Institute of Electrical and Electronics Engineers (IEEE) 802.11.

BACKGROUND

It is important to deliver a time-critical packet in a timely manner while operating in the unlicensed spectrum. This is, however, quite challenging for unlicensed spectrum technologies such as Wi-Fi, especially when a time-critical packet arrives out of schedule (e.g. anomaly is detected and needs to be notified right away or an application generates packets randomly) but there is already another packet occupying the wireless medium, e.g., a packet from a neighboring network or any other wireless transmission that is not managed by the same entity.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the disclosure will be illustrated, by way of example and not limitation, in conjunction with the figures of the accompanying drawings in which like reference numerals refer to similar elements and wherein:

FIG. 1 is a network diagram illustrating an example network environment according to some embodiments of the disclosure.

FIG. 2 is an example of transmission strategy between networks in unlicensed spectrum.

FIG. 3 is an example of transmission strategy between networks in accordance with some embodiments of the disclosure.

FIG. 4 is a flowchart of a method for generation of an ULL packet in accordance with some embodiments of the disclosure.

FIG. 5 is a functional diagram of an exemplary communication station in accordance with one or more example embodiments of the disclosure.

FIG. 6 is a block diagram of an example of a machine or system upon which any one or more of the techniques (e.g., methodologies) discussed herein may be performed.

FIG. 7 is a block diagram of a radio architecture 700A, 700B in accordance with some embodiments that may be implemented in any one of APs 104 and/or the user devices 102 of FIG. 1.

FIG. 8 illustrates WLAN FEM circuitry 704 a in accordance with some embodiments.

FIG. 9 illustrates radio IC circuitry 706 a in accordance with some embodiments.

FIG. 10 illustrates a functional block diagram of baseband processing circuitry 708 a in accordance with some embodiments.

DETAILED DESCRIPTION

Various aspects of the illustrative embodiments will be described using terms commonly employed by those skilled in the art to convey the substance of the disclosure to others skilled in the art. However, it will be apparent to those skilled in the art that many alternate embodiments may be practiced using portions of the described aspects. For purposes of explanation, specific numbers, materials, and configurations are set forth in order to provide a thorough understanding of the illustrative embodiments. However, it will be apparent to those skilled in the art that alternate embodiments may be practiced without the specific details. In other instances, well known features may have been omitted or simplified in order to avoid obscuring the illustrative embodiments.

Further, various operations will be described as multiple discrete operations, in turn, in a manner that is most helpful in understanding the illustrative embodiments; however, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations need not be performed in the order of presentation.

The phrases “in an embodiment” “in one embodiment” and “in some embodiments” are used repeatedly herein. The phrase generally does not refer to the same embodiment; however, it may. The terms “comprising,” “having,” and “including” are synonymous, unless the context dictates otherwise. The phrases “A or B” and “A/B” mean “(A), (B), or (A and B).”

FIG. 1 is a network diagram illustrating an example network environment according to some embodiments of the disclosure. As shown in FIG. 1, a wireless network 100 may include one or more user devices 102 and one or more access points (APs) 104, which may communicate in accordance with IEEE 802.11 communication standards. The user devices 102 may be mobile devices that are non-stationary (e.g., not having fixed locations) or may be stationary devices.

In some embodiments, the user devices 102 and APs 104 may include one or more function modules similar to those in the functional diagram of FIG. 5 and/or the example machine/system of FIG. 6.

The one or more user devices 102 and/or APs 104 may be operable by one or more users 110. It should be noted that any addressable unit may be a station (STA). A STA may take on multiple distinct characteristics, each of which shape its function. For example, a single addressable unit might simultaneously be a portable STA, a quality-of-service (QoS) STA, a dependent STA, and a hidden STA. The one or more user devices 102 and the one or more APs 104 may be STAs. The one or more user devices 102 and/or APs 104 may operate as a personal basic service set (PBSS) control point/access point (PCP/AP). The user devices 102 (e.g., 1024, 1026, or 1028) and/or APs 104 may include any suitable processor-driven device including, but not limited to, a mobile device or a non-mobile, e.g., a static device. For example, the user devices 102 and/or APs 104 may include, a user equipment (UE), a station (STA), an access point (AP), a software enabled AP (SoftAP), a personal computer (PC), a wearable wireless device (e.g., bracelet, watch, glasses, ring, etc.), a desktop computer, a mobile computer, a laptop computer, an Ultrabook™ computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, an internet of things (IoT) device, a sensor device, a personal digital assistant (PDA) device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a non-mobile or non-portable device, a mobile phone, a cellular telephone, a personal communications service (PCS) device, a PDA device which incorporates a wireless communication device, a mobile or portable global positioning system (GPS) device, a digital video broadcasting (DVB) device, a relatively small computing device, a non-desktop computer, a “carry small live large” (CSLL) device, an ultra mobile device (UMD), an ultra mobile PC (UMPC), a mobile internet device (MID), an “origami” device or computing device, a device that supports dynamically composable computing (DCC), a context-aware device, a video device, an audio device, an A/V device, a set-top-box (STB), a blu-ray disc (BD) player, a BD recorder, a digital video disc (DVD) player, a high definition (HD) DVD player, a DVD recorder, a HD DVD recorder, a personal video recorder (PVR), a broadcast HD receiver, a video source, an audio source, a video sink, an audio sink, a stereo tuner, a broadcast radio receiver, a flat panel display, a personal media player (PMP), a digital video camera (DVC), a digital audio player, a speaker, an audio receiver, an audio amplifier, a gaming device, a data source, a data sink, a digital still camera (DSC), a media player, a smartphone, a television, a music player, or the like. Other devices, including smart devices such as lamps, climate control, car components, household components, appliances, etc. may also be included in this list.

As used herein, the term “Internet of Things (IoT) device” is used to refer to any object (e.g., an appliance, a sensor, etc.) that has an addressable interface (e.g., an Internet protocol (IP) address, a Bluetooth identifier (ID), a near-field communication (NFC) ID, etc.) and can transmit information to one or more other devices over a wired or wireless connection. An IoT device may have a passive communication interface, such as a quick response (QR) code, a radio-frequency identification (RFID) tag, an NFC tag, or the like, or an active communication interface, such as a modem, a transceiver, a transmitter-receiver, or the like. An IoT device can have a particular set of attributes (e.g., a device state or status, such as whether the IoT device is on or off, open or closed, idle or active, available for task execution or busy, and so on, a cooling or heating function, an environmental monitoring or recording function, a light-emitting function, a sound-emitting function, etc.) that can be embedded in and/or controlled/monitored by a central processing unit (CPU), microprocessor, ASIC, or the like, and configured for connection to an IoT network such as a local ad-hoc network or the Internet. For example, IoT devices may include, but are not limited to, refrigerators, toasters, ovens, microwaves, freezers, dishwashers, dishes, hand tools, clothes washers, clothes dryers, furnaces, air conditioners, thermostats, televisions, light fixtures, vacuum cleaners, sprinklers, electricity meters, gas meters, etc., so long as the devices are equipped with an addressable communications interface for communicating with the IoT network. IoT devices may also include cell phones, desktop computers, laptop computers, tablet computers, personal digital assistants (PDAs), etc. Accordingly, the IoT network may be comprised of a combination of “legacy” Internet-accessible devices (e.g., laptop or desktop computers, cell phones, etc.) in addition to devices that do not typically have Internet-connectivity (e.g., dishwashers, etc.).

The user devices 102 and/or APs 104 may also include mesh stations in, for example, a mesh network, in accordance with one or more IEEE 802.11 standards and/or 3GPP standards.

Any of the user devices 102 (e.g., user devices 1024, 1026, 1028) and APs 104 may be configured to communicate with each other via one or more communications networks 130 and/or 135 wirelessly or wired. The user devices 102 may also communicate peer-to-peer or directly with each other with or without APs 104. Any of the communications networks 130 and/or 135 may include, but not limited to, any one of a combination of different types of suitable communications networks such as, for example, broadcasting networks, cable networks, public networks (e.g., the Internet), private networks, wireless networks, cellular networks, or any other suitable private and/or public networks. Further, any of the communications networks 130 and/or 135 may have any suitable communication range associated therewith and may include, for example, global networks (e.g., the Internet), metropolitan area networks (MANs), wide area networks (WANs), local area networks (LANs), or personal area networks (PANs). In addition, any of the communications networks 130 and/or 135 may include any type of medium over which network traffic may be carried including, but not limited to, coaxial cable, twisted-pair wire, optical fiber, a hybrid fiber coaxial (HFC) medium, microwave terrestrial transceivers, radio frequency communication mediums, white space communication mediums, ultra-high frequency communication mediums, satellite communication mediums, or any combination thereof.

Any of the user devices 102 (e.g., user devices 1024, 1026, 1028) and APs 104 may include one or more communications antennas. The one or more communications antennas may be any suitable type of antennas corresponding to the communications protocols used by the user devices 102 (e.g., user devices 1024, 1026 and 1028) and APs 104. Some non-limiting examples of suitable communications antennas include Wi-Fi antennas, Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards compatible antennas, directional antennas, non-directional antennas, dipole antennas, folded dipole antennas, patch antennas, multiple-input multiple-output (MIMO) antennas, omnidirectional antennas, quasi-omnidirectional antennas, or the like. The one or more communications antennas may be communicatively coupled to a radio component to transmit and/or receive signals, such as communications signals to and/or from the user devices 102 and/or APs 104.

Any of the user devices 102 (e.g., user devices 1024, 1026, 1028) and APs 104 may be configured to perform directional transmission and/or directional reception in conjunction with wirelessly communicating in a wireless network. Any of the user devices 102 (e.g., user devices 1024, 1026, 1028) and APs 104 may be configured to perform such directional transmission and/or reception using a set of multiple antenna arrays (e.g., DMG antenna arrays or the like). Each of the multiple antenna arrays may be used for transmission and/or reception in a particular respective direction or range of directions. Any of the user devices 102 (e.g., user devices 1024, 1026, 1028) and APs 104 may be configured to perform any given directional transmission towards one or more defined transmit sectors. Any of the user devices 102 (e.g., user devices 1024, 1026, 1028) and APs 104 may be configured to perform any given directional reception from one or more defined receive sectors.

MIMO beamforming in a wireless network may be accomplished using radio frequency (RF) beamforming and/or digital beamforming. In some embodiments, in performing a given MIMO transmission, the user devices 102 and/or APs 104 may be configured to use all or a subset of its one or more communications antennas to perform MIMO beamforming.

Any of the user devices 102 (e.g., user devices 1024, 1026, 1028) and APs 104 may include any suitable radio and/or transceiver for transmitting and/or receiving radio frequency (RF) signals in the bandwidth and/or channels corresponding to the communications protocols utilized by any of the user devices 102 and APs 104 to communicate with each other. The radio components may include hardware and/or software to modulate and/or demodulate communications signals according to pre-established transmission protocols. The radio components may further have hardware and/or software instructions to communicate via one or more Wi-Fi and/or Wi-Fi direct protocols, as standardized by the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards. It should be understood that this list of communication channels in accordance with certain 802.11 standards is only a partial list and that other 802.11 standards may be used (e.g., Next Generation Wi-Fi, or other standards). In some embodiments, non-Wi-Fi protocols may be used for communications between devices, such as Bluetooth, dedicated short-range communication (DSRC), Ultra-High Frequency (UHF) (e.g. IEEE 802.11af, IEEE 802.22), white band frequency (e.g., white spaces), or other packetized radio communications. The radio component may include any known receiver and baseband suitable for communicating via the communications protocols. The radio component may further include a low noise amplifier (LNA), additional signal amplifiers, an analog-to-digital (A/D) converter, one or more buffers, and digital baseband.

As mentioned above, delivering a time-critical packet in a timely manner while operating in the unlicensed spectrum is quite challenging for unlicensed spectrum technologies such as Wi-Fi, especially when a time-critical packet arrives out of schedule (e.g. anomaly is detected and needs to be notified right away or an application generates packets randomly) but there is already another packet occupying the wireless medium, e.g., a packet from a neighboring network or any other wireless transmission that is not managed by the same entity.

A problem of IEEE 802.11 (Wi-Fi) design for an ultra-low latency (ULL) application includes increased latency due to Listen-before-talk (LBT). In such a Wi-Fi design, when the wireless medium is busy, a transmission needs be deferred until the medium becomes idle.

In addition, when the wireless medium is idle, a transmitter needs to do random backoff to avoid collision with the ongoing transmission, which adds overheads in time and prevents timely delivery of a packet.

Furthermore, time overhead may further increase due to the legacy preamble. Since there are old and new generations of IEEE 802.11 (e.g. 802.11a/b/g/n/ac/ax/be/ . . . ) coexisting in the unlicensed spectrum, every new generation of IEEE 802.11 adds a ‘legacy preamble’, which is an Orthogonal Frequency Division Multiplexing (OFDM) non-High Throughput (HT) Physical Protocol Data Unit (PPDU) preamble (legacy Short-training Field (STF)+ legacy Long-training Field (LTF)+Legacy Signal (L-SIG) fields), in front of new PPDU formats, so that old generation IEEE 802.11 can understand that there is an IEEE 802.11 packet on the medium and how long the wireless medium will be occupied by the packet. This prevents an older generation of IEEE 802.11 from transmitting while a new generation IEEE 802.11 packet is being transmitted and avoids potential collision between old and new IEEE 802.11 packet transmissions. However, this adds an overhead of 20 microseconds (as the legacy preamble is 20 microseconds long) to every packet transmission and increases latency for an ULL application. Herein, the term of “microsecond” is interchangeable with “usec” and “us”.

FIG. 2 is an example of transmission strategy between networks in unlicensed spectrum. As shown in FIG. 2, in the IEEE 802.11 network, an unscheduled urgent data arrives, but the wireless channel is occupied by an Overlapping Basic Service Set (OBSS) packet exchange from a neighboring OBSS network, thus the unscheduled urgent data needs to wait until the channel becomes idle. This latency is a major issue for many ultra-low latency and time-critical applications. When the wireless medium is idle, a transmitter of the IEEE 802.11 network needs to do random backoff to avoid collision with the ongoing transmission, which adds overheads in time due to channel access and prevents timely delivery of a packet. In addition, the packet includes legacy preamble which adds an overhead of 20 microseconds, which further increases the latency for the data transmission.

In a further aspect, in an IEEE 802.11 network before IEEE 802.11ax, an OFDM symbol was 4 microseconds (with 0.8 usec guard interval) long due to 64-point Fast Fourier Transformation (FFT) (64-pt FFT) over 20 MHz signal bandwidth. In IEEE 802.11ax, an OFDM symbol is increased to 13.6 microseconds (with 0.8 usec guard interval) due to 4× more tones in the same signal bandwidth. The increased time scale makes the new preamble longer (each field in units of 4 or 16 microseconds) and adds overhead, so that the latency for a packet is eventually increased.

In the embodiments of the present disclosure, PHY and MAC design for IEEE 802.11 is proposed to enable ultra-low latency (e.g., <10-100 microseconds) for a time critical packet delivery for an ultra-low latency application in an unmanaged network environment. The packet for the ultra-low latency application designed according to the embodiments of the present disclosure may be referred as to ULL packet herein.

In some embodiments, a duration of the ULL packet is less than 20 microseconds. In some embodiments, since the ULL packet is very short (less than the length of the legacy preamble), the legacy preamble (20 usec) is no longer needed to protect the ULL packet, thus the ULL packet excludes the legacy preamble.

An example of the ULL PPDU format is illustrated below. It includes an ULL-STF, an ULL-LTF, an ULL-SIG and a Data portion. There is no legacy preamble (L-STF, L-LTF, and L-SIG fields) in the ULL PPDU format.

ULL-STF ULL-LTF ULL-SIG Data

In some embodiments, a wideband signal (e.g. 80 MHz or 160 MHz in 6 GHz band) with a fewer number of tones (e.g. 64-pt FFT) to may be used to generate the ULL packet.

In some embodiments, a 4× or 8× smaller time scale OFDM symbol is generated for the ULL packet. For example, 4× smaller time scale is achieved when 64-pt FFT is used over 80 MHz channel bandwidth for IEEE 802.11ac PHY (normally 256-pt FFT is used over 80 MHz). Since a tone spacing for the ULL packet is 4× larger than IEEE 802.11ac OFDM design, the time scale shrinks by 4×. Similarly, 8× smaller time scale is achieved when 64-pt FFT is used on 160 MHz channel bandwidth, which makes the tone spacing for the ULL packet to increase by 8× times compared to 20 Mhz channel case, so that the time scale shrinks by 8×.

In some embodiments, a subcarrier frequency spacing for the ULL packet is greater than 312.5 kHz (e.g., for IEEE 802.11ac).

In some embodiments, an OFDM symbol duration for the ULL packet is less than 3.2 microseconds (e.g., for IEEE 802.11ac).

In some embodiments, a duration of a short-training field (e.g., the ULL-STF) for the ULL packet is less than 4 microseconds (e.g., for HE-STF).

In some embodiments, a duration of a long-training field (e.g., the ULL-LTF) for the ULL packet is less than 4 microseconds (e.g., for HE-LTF).

In some embodiments, a signal field (e.g., the ULL-SIG) for the ULL packet includes 2 OFDM symbols.

Below, some implementation examples for the ULL packet are illustrated. However, other implementation may be applicable according to the concept of the present disclosure, which is not limited in this respect.

-   -   1. 4× smaller time scale design over 80 MHz: 64-tones over an 80         MHz signal bandwidth         -   a. Subcarrier frequency spacing: 1.25 MHz         -   b. IDFT/DFT period: 0.8 usec         -   c. Guard interval duration: 0.8 usec         -   d. OFDM symbol duration: 1.6 usec         -   e. Short-training field duration: 2 usec         -   f. Long-training field duration: 0.8×2 usec+guard             interval=2.4 usec         -   g. Signal field: 2 OFDM symbols=3.2 usec         -   h. Total preamble length=e+f+g=7.6 usec         -   i. Number OFDM symbols for the Data field of the packet less             than 20 usec=floor{(20−7.6)/1.6}=7 OFDM symbols             -   i. 1ss MCSO: 7 OFDM symbols×26 bits=22 bytes in the Data                 field             -   ii. 1ss MCS8: 7 OFDM symbols×312 bits=273 bytes in the                 Data field     -   2. 4× smaller time scale design over 160 MHz: 128-tones over a         160 MHz signal bandwidth         -   a. Subcarrier frequency spacing: 1.25 MHz         -   b. IDFT/DFT period: 0.8 usec         -   c. Guard interval duration: 0.8 usec         -   d. OFDM symbol duration: 1.6 usec         -   e. Short-training field duration: 2 usec         -   f. Long-training field duration: 0.8×2 usec+guard             interval=2.4 usec         -   g. Signal field: 2 OFDM symbols=3.2 usec         -   h. Total preamble length=e+f+g=7.6 usec         -   i. Number OFDM symbols for the Data field of the packet less             than 20 usec=floor{(20−7.6)/1.6}=7 OFDM symbols             -   i. 1ss MCSO: 7 OFDM symbols×54 bits=47 bytes in the Data                 field             -   ii. 1ss MCS9: 7 OFDM symbols×720 bits=630 bytes in the                 Data field     -   3. 8× smaller time scale design over 160 MHz: 64-tones over a         160 MHz signal bandwidth         -   a. Subcarrier frequency spacing: 2.5 MHz         -   b. IDFT/DFT period: 0.4 usec         -   c. Guard interval duration: 0.4 usec (shorten guard interval             by half of 0.8 usec)         -   d. OFDM symbol duration: 0.8 usec         -   e. Short-training field duration: 1 usec         -   f. Long-training field duration: 0.4×2 usec+guard             interval=1.2 usec         -   g. Signal field: 2 OFDM symbols=1.6 usec         -   h. Total preamble length=e+f+g=3.8 usec         -   i. Number OFDM symbols for the Data field of the packet less             than 10 usec=floor{(10−3.8)/0.8}=7 OFDM symbols             -   i. 1ss MCSO: 7 OFDM symbols×26 bits=22 bytes in the Data                 field             -   ii. 1ss MCS8: 7 OFDM symbols×312 bits=273 bytes in the                 Data field

In some embodiments, the ULL packet is transmitted even if the wireless medium is busy (e.g. there is OBSS traffic or interference from a non-802.11 system (e.g. fifth generation (5G) New Radio (NR) in Unlicensed spectrum (5GNR-U)) on the wireless medium). Due to extremely short packet length (<20 usec), the interference from the ultra-short ULL packet on the ongoing OB SS transmission is minimal. For the potential interference from the ongoing OBSS transmission on the ULL packet, it could be low enough, for example, when there is a proper frequency planning or the OBSS transmission is in a different room/building. In addition, the ULL packet could use a robust Modulation and Coding Scheme (MCS) or an interference mitigation technique (e.g., more robust channel coding or waveform design such as spread spectrum technique). The ULL packet transmission and the ongoing OBSS traffic may be partially or fully overlapping in frequency regardless of the measured power level.

FIG. 3 is an example of transmission strategy between networks in accordance with some embodiments of the disclosure. As shown in FIG. 3, the urgent data of the IEEE 802.11 network arrives when the wireless channel is occupied by the ongoing OBSS packet. The urgent data may be transmitted without delay and channel access/legacy preamble overhead.

In some embodiments, in order to enhance the reliability of ULL packet reception, the ULL packet may be encoded with dual-carrier modulation (DCM) similar to that adopted in IEE 802.11ax or quad-carrier modulation that combines four tones to encode/decode one tone value. The additional coding makes the packet size longer but not larger than 50 usec which is estimated when 128-tones over 160 MHz signal bandwidth is used.

In some embodiments, the 6 GHz operation is only allowed indoor and used in an infrastructure mode, then the STA is expected to be much closer to the AP than neighboring OBSS networks.

In some embodiments, the ULL packet transmission may not occupy the wireless medium longer than allowed by European Telecommunication Standards Institute (ETSI) rules. For example, the ULL packet transmission may follow the duty cycle and channel occupancy time rules defined in the ETSI. In some embodiments, the ULL packet transmission may follow other rules. The present disclosure is not limited in this respect.

In some embodiments, the ULL packet may be identified by a STA before transmission using a higher layer packet classification tag, a MAC layer traffic flow identifier (ID) or a traffic Identifier (TID) that is defined for identifying ULL packets.

In some embodiments, the size of the ULL packet is equal to or less than a predefined packet size threshold. In some embodiments, the duration of the ULL packet is equal to or less than a predefined packet duration threshold. The packet size limit in terms of number of bits or in terms of packet duration in time can be used by a STA to decide whether a packet is allowed to be classified as ULL packet and use the ULL PHY/MAC features.

FIG. 4 is a flowchart of a method 400 for generation of an ULL packet in accordance with some embodiments of the disclosure. The method 400 may include steps 410 and 420, which may be implemented by a STA, for example.

At 410, an ULL packet is encoded. The duration of the ULL packet is less than 20 microseconds.

At 420, the ULL packet is transmitted to an AP in an unlicensed spectrum.

The method 400 may include more or less or different steps, which is not limited in the disclosure.

The ULL packet of the present disclosure may have a short duration by using wider signal bandwidth, larger subcarrier spacing, and the like. In this way, the ULL packet can be transmitted without delay even when the wireless medium is occupied by ongoing OBSS transmission.

FIG. 5 shows a functional diagram of an exemplary communication station 500, in accordance with one or more example embodiments of the disclosure. In one embodiment, FIG. 5 illustrates a functional block diagram of a communication station that may be suitable for use as the AP 104 (FIG. 1) or the user device 102 (FIG. 1) in accordance with some embodiments. The communication station 500 may also be suitable for use as a handheld device, a mobile device, a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a wearable computer device, a femtocell, a high data rate (HDR) subscriber station, an access point, an access terminal, or other personal communication system (PCS) device.

The communication station 500 may include communications circuitry 502 and a transceiver 510 for transmitting and receiving signals to and from other communication stations using one or more antennas 501. The communications circuitry 502 may include circuitry that can operate the physical layer (PHY) communications and/or medium access control (MAC) communications for controlling access to the wireless medium, and/or any other communications layers for transmitting and receiving signals. The communication station 500 may also include processing circuitry 506 and memory 508 arranged to perform the operations described herein. In some embodiments, the communications circuitry 502 and the processing circuitry 506 may be configured to perform operations detailed in the above figures, diagrams, and flows.

In accordance with some embodiments, the communications circuitry 502 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium. The communications circuitry 502 may be arranged to transmit and receive signals. The communications circuitry 502 may also include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc. In some embodiments, the processing circuitry 506 of the communication station 500 may include one or more processors. In other embodiments, two or more antennas 501 may be coupled to the communications circuitry 502 arranged for transmitting and receiving signals. The memory 508 may store information for configuring the processing circuitry 506 to perform operations for configuring and transmitting message frames and performing the various operations described herein. The memory 508 may include any type of memory, including non-transitory memory, for storing information in a form readable by a machine (e.g., a computer). For example, the memory 508 may include a computer-readable storage device, read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices and other storage devices and media.

In some embodiments, the communication station 500 may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.

In some embodiments, the communication station 500 may include one or more antennas 501. The antennas 501 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals. In some embodiments, instead of two or more antennas, a single antenna with multiple apertures may be used. In these embodiments, each aperture may be considered a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated for spatial diversity and the different channel characteristics that may result between each of the antennas and the antennas of a transmitting station.

In some embodiments, the communication station 500 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements. The display may be a liquid crystal display (LCD) screen including a touch screen.

Although the communication station 500 is illustrated as having several separate functional elements, two or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements of the communication station 500 may refer to one or more processes operating on one or more processing elements.

Certain embodiments may be implemented in one or a combination of hardware, firmware, and software. Other embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein. A computer-readable storage device may include any non-transitory memory mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a computer-readable storage device may include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media. In some embodiments, the communication station 500 may include one or more processors and may be configured with instructions stored on a computer-readable storage device.

FIG. 6 illustrates a block diagram of an example of a machine or system 600 upon which any one or more of the techniques (e.g., methodologies) discussed herein may be performed. In other embodiments, the machine 600 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine 600 may operate in the capacity of a server machine, a client machine, or both in server-client network environments. In an example, the machine 600 may act as a peer machine in peer-to-peer (P2P) (or other distributed) network environments. The machine 600 may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile telephone, a wearable computer device, a web appliance, a network router, a switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine, such as a base station. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), or other computer cluster configurations.

Examples, as described herein, may include or may operate on logic or a number of components, modules, or mechanisms. Modules are tangible entities (e.g., hardware) capable of performing specified operations when operating. A module includes hardware. In an example, the hardware may be specifically configured to carry out a specific operation (e.g., hardwired). In another example, the hardware may include configurable execution units (e.g., transistors, circuits, etc.) and a computer readable medium containing instructions where the instructions configure the execution units to carry out a specific operation when in operation. The configuring may occur under the direction of the executions units or a loading mechanism. Accordingly, the execution units are communicatively coupled to the computer-readable medium when the device is operating. In this example, the execution units may be a member of more than one module. For example, under operation, the execution units may be configured by a first set of instructions to implement a first module at one point in time and reconfigured by a second set of instructions to implement a second module at a second point in time.

The machine (e.g., computer system) 600 may include a hardware processor 602 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 604 and a static memory 606, some or all of which may communicate with each other via an interlink (e.g., bus) 608. The machine 600 may further include a power management device 632, a graphics display device 610, an alphanumeric input device 612 (e.g., a keyboard), and a user interface (UI) navigation device 614 (e.g., a mouse). In an example, the graphics display device 610, alphanumeric input device 612, and UI navigation device 614 may be a touch screen display. The machine 600 may additionally include a storage device (i.e., drive unit) 616, a signal generation device 618 (e.g., a speaker), an ULL packet generation device 619, a network interface device/transceiver 620 coupled to antenna(s) 630, and one or more sensors 628, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensor. The machine 600 may include an output controller 634, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.)). The operations in accordance with one or more example embodiments of the disclosure may be carried out by a baseband processor. The baseband processor may be configured to generate corresponding baseband signals. The baseband processor may further include physical layer (PHY) and medium access control layer (MAC) circuitry, and may further interface with the hardware processor 602 for generation and processing of the baseband signals and for controlling operations of the main memory 604, the storage device 616, and/or the ULL packet generation device 619. The baseband processor may be provided on a single radio card, a single chip, or an integrated circuit (IC).

The storage device 616 may include a machine readable medium 622 on which is stored one or more sets of data structures or instructions 624 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 624 may also reside, completely or at least partially, within the main memory 604, within the static memory 606, or within the hardware processor 602 during execution thereof by the machine 600. In an example, one or any combination of the hardware processor 602, the main memory 604, the static memory 606, or the storage device 616 may constitute machine-readable media.

The ULL packet generation device 619 may carry out or perform any of the operations and processes (e.g., method 400) described and shown above.

It is understood that the above are only a subset of what the ULL packet generation 619 may be configured to perform and that other functions included throughout this disclosure may also be performed by the ULL packet generation device 619.

While the machine-readable medium 622 is illustrated as a single medium, the term “machine-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 624.

Various embodiments may be implemented fully or partially in software and/or firmware. This software and/or firmware may take the form of instructions contained in or on a non-transitory computer-readable storage medium. Those instructions may then be read and executed by one or more processors to enable performance of the operations described herein. The instructions may be in any suitable form, such as but not limited to source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. Such a computer-readable medium may include any tangible non-transitory medium for storing information in a form readable by one or more computers, such as but not limited to read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; a flash memory, etc.

The term “machine-readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 600 and that cause the machine 600 to perform any one or more of the techniques of the disclosure, or that is capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting machine-readable medium examples may include solid-state memories and optical and magnetic media. In an example, a massed machine-readable medium includes a machine-readable medium with a plurality of particles having resting mass. Specific examples of massed machine-readable media may include non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), or electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

The instructions 624 may further be transmitted or received over a communications network 626 using a transmission medium via the network interface device/transceiver 620 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communications networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), plain old telephone (POTS) networks, wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, and peer-to-peer (P2P) networks, among others. In an example, the network interface device/transceiver 620 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 626. In an example, the network interface device/transceiver 620 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques. The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine 600 and includes digital or analog communications signals or other intangible media to facilitate communication of such software.

FIG. 7 is a block diagram of a radio architecture 700A, 700B in accordance with some embodiments that may be implemented in any one of APs 104 and/or the user devices 102 of FIG. 1. Radio architecture 700A, 700B may include radio front-end module (FEM) circuitry 704 a-b, radio IC circuitry 706 a-b and baseband processing circuitry 708 a-b. Radio architecture 700A, 700B as shown includes both Wireless Local Area Network (WLAN) functionality and Bluetooth (BT) functionality although embodiments are not so limited. In this disclosure, “WLAN” and “Wi-Fi” are used interchangeably.

FEM circuitry 704 a-b may include a WLAN or Wi-Fi FEM circuitry 704 a and a Bluetooth (BT) FEM circuitry 704 b. The WLAN FEM circuitry 704 a may include a receive signal path comprising circuitry configured to operate on WLAN RF signals received from one or more antennas 701, to amplify the received signals and to provide the amplified versions of the received signals to the WLAN radio IC circuitry 706 a for further processing. The BT FEM circuitry 704 b may include a receive signal path which may include circuitry configured to operate on BT RF signals received from one or more antennas 701, to amplify the received signals and to provide the amplified versions of the received signals to the BT radio IC circuitry 706 b for further processing. FEM circuitry 704 a may also include a transmit signal path which may include circuitry configured to amplify WLAN signals provided by the radio IC circuitry 706 a for wireless transmission by one or more of the antennas 701. In addition, FEM circuitry 704 b may also include a transmit signal path which may include circuitry configured to amplify BT signals provided by the radio IC circuitry 706 b for wireless transmission by the one or more antennas. In the embodiment of FIG. 7, although FEM 704 a and FEM 704 b are shown as being distinct from one another, embodiments are not so limited, and include within their scope the use of an FEM (not shown) that includes a transmit path and/or a receive path for both WLAN and BT signals, or the use of one or more FEM circuitries where at least some of the FEM circuitries share transmit and/or receive signal paths for both WLAN and BT signals.

Radio IC circuitry 706 a-b as shown may include WLAN radio IC circuitry 706 a and BT radio IC circuitry 706 b. The WLAN radio IC circuitry 706 a may include a receive signal path which may include circuitry to down-convert WLAN RF signals received from the FEM circuitry 704 a and provide baseband signals to WLAN baseband processing circuitry 708 a. BT radio IC circuitry 706 b may in turn include a receive signal path which may include circuitry to down-convert BT RF signals received from the FEM circuitry 704 b and provide baseband signals to BT baseband processing circuitry 708 b. WLAN radio IC circuitry 706 a may also include a transmit signal path which may include circuitry to up-convert WLAN baseband signals provided by the WLAN baseband processing circuitry 708 a and provide WLAN RF output signals to the FEM circuitry 704 a for subsequent wireless transmission by the one or more antennas 701. BT radio IC circuitry 706 b may also include a transmit signal path which may include circuitry to up-convert BT baseband signals provided by the BT baseband processing circuitry 708 b and provide BT RF output signals to the FEM circuitry 704 b for subsequent wireless transmission by the one or more antennas 701. In the embodiment of FIG. 7, although radio IC circuitries 706 a and 706 b are shown as being distinct from one another, embodiments are not so limited, and include within their scope the use of a radio IC circuitry (not shown) that includes a transmit signal path and/or a receive signal path for both WLAN and BT signals, or the use of one or more radio IC circuitries where at least some of the radio IC circuitries share transmit and/or receive signal paths for both WLAN and BT signals.

Baseband processing circuitry 708 a-b may include a WLAN baseband processing circuitry 708 a and a BT baseband processing circuitry 708 b. The WLAN baseband processing circuitry 708 a may include a memory, such as, for example, a set of RAM arrays in a Fast Fourier Transform or Inverse Fast Fourier Transform block (not shown) of the WLAN baseband processing circuitry 708 a. Each of the WLAN baseband circuitry 708 a and the BT baseband circuitry 708 b may further include one or more processors and control logic to process the signals received from the corresponding WLAN or BT receive signal path of the radio IC circuitry 706 a-b, and to also generate corresponding WLAN or BT baseband signals for the transmit signal path of the radio IC circuitry 706 a-b. Each of the baseband processing circuitries 708 a and 708 b may further include physical layer (PHY) and medium access control layer (MAC) circuitry, and may further interface with a device for generation and processing of the baseband signals and for controlling operations of the radio IC circuitry 706 a-b.

Referring still to FIG. 7, according to the shown embodiment, WLAN-BT coexistence circuitry 713 may include logic providing an interface between the WLAN baseband circuitry 708 a and the BT baseband circuitry 708 b to enable use cases requiring WLAN and BT coexistence. In addition, a switch 703 may be provided between the WLAN FEM circuitry 704 a and the BT FEM circuitry 704 b to allow switching between the WLAN and BT radios according to application needs. In addition, although the antennas 701 are depicted as being respectively connected to the WLAN FEM circuitry 704 a and the BT FEM circuitry 704 b, embodiments include within their scope the sharing of one or more antennas as between the WLAN and BT FEMs, or the provision of more than one antenna connected to each of FEM 704 a or 704 b.

In some embodiments, the front-end module circuitry 704 a-b, the radio IC circuitry 706 a-b, and baseband processing circuitry 708 a-b may be provided on a single radio card, such as wireless radio card 702. In some other embodiments, the one or more antennas 701, the FEM circuitry 704 a-b and the radio IC circuitry 706 a-b may be provided on a single radio card. In some other embodiments, the radio IC circuitry 706 a-b and the baseband processing circuitry 708 a-b may be provided on a single chip or integrated circuit (IC), such as IC 712.

In some embodiments, the wireless radio card 702 may include a WLAN radio card and may be configured for Wi-Fi communications, although the scope of the embodiments is not limited in this respect. In some of these embodiments, the radio architecture 700A, 700B may be configured to receive and transmit orthogonal frequency division multiplexed (OFDM) or orthogonal frequency division multiple access (OFDMA) communication signals over a multicarrier communication channel. The OFDM or OFDMA signals may comprise a plurality of orthogonal subcarriers.

In some of these multicarrier embodiments, radio architecture 700A, 700B may be part of a Wi-Fi communication station (STA) such as a wireless access point (AP), a base station or a mobile device including a Wi-Fi device. In some of these embodiments, radio architecture 700A, 700B may be configured to transmit and receive signals in accordance with specific communication standards and/or protocols, such as any of the Institute of Electrical and Electronics Engineers (IEEE) standards including, 802.11n-2009, IEEE 802.11-2012, IEEE 802.11-2016, 802.11n-2009, 802.11ac, 802.11ah, 802.11ad, 802.11 ay and/or 802.11ax standards and/or proposed specifications for WLANs, although the scope of embodiments is not limited in this respect. Radio architecture 700A, 700B may also be suitable to transmit and/or receive communications in accordance with other techniques and standards.

In some embodiments, the radio architecture 700A, 700B may be configured for high-efficiency Wi-Fi (HEW) communications in accordance with the IEEE 802.11ax standard. In these embodiments, the radio architecture 700A, 700B may be configured to communicate in accordance with an OFDMA technique, although the scope of the embodiments is not limited in this respect.

In some other embodiments, the radio architecture 700A, 700B may be configured to transmit and receive signals transmitted using one or more other modulation techniques such as spread spectrum modulation (e.g., direct sequence code division multiple access (DS-CDMA) and/or frequency hopping code division multiple access (FH-CDMA)), time-division multiplexing (TDM) modulation, and/or frequency-division multiplexing (FDM) modulation, although the scope of the embodiments is not limited in this respect.

In some embodiments, as further shown in FIG. 7, the BT baseband circuitry 708 b may be compliant with a Bluetooth (BT) connectivity standard such as Bluetooth, Bluetooth 8.0 or Bluetooth 6.0, or any other iteration of the Bluetooth Standard.

In some embodiments, the radio architecture 700A, 700B may include other radio cards, such as a cellular radio card configured for cellular (e.g., 5GPP such as LTE, LTE-Advanced or 5G communications).

In some IEEE 802.11 embodiments, the radio architecture 700A, 700B may be configured for communication over various channel bandwidths including bandwidths having center frequencies of about 900 MHz, 2.4 GHz, 5 GHz, and bandwidths of about 2 MHz, 4 MHz, 5 MHz, 5.5 MHz, 6 MHz, 8 MHz, 10 MHz, 20 MHz, 40 MHz, 80 MHz (with contiguous bandwidths) or 80+80 MHz (160 MHz) (with non-contiguous bandwidths). In some embodiments, a 720 MHz channel bandwidth may be used. The scope of the embodiments is not limited with respect to the above center frequencies however.

FIG. 8 illustrates WLAN FEM circuitry 704 a in accordance with some embodiments. Although the example of FIG. 8 is described in conjunction with the WLAN FEM circuitry 704 a, the example of FIG. 8 may be described in conjunction with the example BT FEM circuitry 704 b (FIG. 7), although other circuitry configurations may also be suitable.

In some embodiments, the FEM circuitry 704 a may include a TX/RX switch 802 to switch between transmit mode and receive mode operation. The FEM circuitry 704 a may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 704 a may include a low-noise amplifier (LNA) 806 to amplify received RF signals 803 and provide the amplified received RF signals 807 as an output (e.g., to the radio IC circuitry 706 a-b (FIG. 7)). The transmit signal path of the circuitry 704 a may include a power amplifier (PA) to amplify input RF signals 809 (e.g., provided by the radio IC circuitry 706 a-b), and one or more filters 812, such as band-pass filters (BPFs), low-pass filters (LPFs) or other types of filters, to generate RF signals 815 for subsequent transmission (e.g., by one or more of the antennas 701 (FIG. 7)) via an example duplexer 814.

In some dual-mode embodiments for Wi-Fi communication, the FEM circuitry 704 a may be configured to operate in either the 2.4 GHz frequency spectrum or the 5 GHz frequency spectrum. In these embodiments, the receive signal path of the FEM circuitry 704 a may include a receive signal path duplexer 804 to separate the signals from each spectrum as well as provide a separate LNA 806 for each spectrum as shown. In these embodiments, the transmit signal path of the FEM circuitry 704 a may also include a power amplifier 810 and a filter 812, such as a BPF, an LPF or another type of filter for each frequency spectrum and a transmit signal path duplexer 814 to provide the signals of one of the different spectrums onto a single transmit path for subsequent transmission by the one or more of the antennas 701 (FIG. 7). In some embodiments, BT communications may utilize the 2.4 GHz signal paths and may utilize the same FEM circuitry 704 a as the one used for WLAN communications.

FIG. 9 illustrates radio IC circuitry 706 a in accordance with some embodiments. The radio IC circuitry 706 a is one example of circuitry that may be suitable for use as the WLAN or BT radio IC circuitry 706 a/706 b (FIG. 7), although other circuitry configurations may also be suitable. Alternatively, the example of FIG. 9 may be described in conjunction with the example BT radio IC circuitry 706 b.

In some embodiments, the radio IC circuitry 706 a may include a receive signal path and a transmit signal path. The receive signal path of the radio IC circuitry 706 a may include at least mixer circuitry 902, such as, for example, down-conversion mixer circuitry, amplifier circuitry 906 and filter circuitry 908. The transmit signal path of the radio IC circuitry 706 a may include at least filter circuitry 912 and mixer circuitry 914, such as, for example, up-conversion mixer circuitry. Radio IC circuitry 706 a may also include synthesizer circuitry 904 for synthesizing a frequency 905 for use by the mixer circuitry 902 and the mixer circuitry 914. The mixer circuitry 902 and/or 914 may each, according to some embodiments, be configured to provide direct conversion functionality. The latter type of circuitry presents a much simpler architecture as compared with standard super-heterodyne mixer circuitries, and any flicker noise brought about by the same may be alleviated for example through the use of OFDM modulation. FIG. 9 illustrates only a simplified version of a radio IC circuitry, and may include, although not shown, embodiments where each of the depicted circuitries may include more than one component. For instance, mixer circuitry 914 may each include one or more mixers, and filter circuitries 908 and/or 912 may each include one or more filters, such as one or more BPFs and/or LPFs according to application needs. For example, when mixer circuitries are of the direct-conversion type, they may each include two or more mixers.

In some embodiments, mixer circuitry 902 may be configured to down-convert RF signals 807 received from the FEM circuitry 704 a-b (FIG. 7) based on the synthesized frequency 905 provided by synthesizer circuitry 904. The amplifier circuitry 906 may be configured to amplify the down-converted signals and the filter circuitry 908 may include an LPF configured to remove unwanted signals from the down-converted signals to generate output baseband signals 907. Output baseband signals 907 may be provided to the baseband processing circuitry 708 a-b (FIG. 7) for further processing. In some embodiments, the output baseband signals 907 may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 902 may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 914 may be configured to up-convert input baseband signals 911 based on the synthesized frequency 905 provided by the synthesizer circuitry 904 to generate RF output signals 809 for the FEM circuitry 704 a-b. The baseband signals 911 may be provided by the baseband processing circuitry 708 a-b and may be filtered by filter circuitry 912. The filter circuitry 912 may include an LPF or a BPF, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 902 and the mixer circuitry 914 may each include two or more mixers and may be arranged for quadrature down-conversion and/or up-conversion respectively with the help of synthesizer 904. In some embodiments, the mixer circuitry 902 and the mixer circuitry 914 may each include two or more mixers each configured for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 902 and the mixer circuitry 914 may be arranged for direct down-conversion and/or direct up-conversion, respectively. In some embodiments, the mixer circuitry 902 and the mixer circuitry 914 may be configured for super-heterodyne operation, although this is not a requirement.

Mixer circuitry 902 may comprise, according to one embodiment: quadrature passive mixers (e.g., for the in-phase (I) and quadrature phase (Q) paths). In such an embodiment, RF input signal 807 from FIG. 9 may be down-converted to provide I and Q baseband output signals to be transmitted to the baseband processor.

Quadrature passive mixers may be driven by zero and ninety-degree time-varying LO switching signals provided by a quadrature circuitry which may be configured to receive a LO frequency (fLO) from a local oscillator or a synthesizer, such as LO frequency 905 of synthesizer 904 (FIG. 9). In some embodiments, the LO frequency may be the carrier frequency, while in other embodiments, the LO frequency may be a fraction of the carrier frequency (e.g., one-half the carrier frequency, one-third the carrier frequency). In some embodiments, the zero and ninety-degree time-varying switching signals may be generated by the synthesizer, although the scope of the embodiments is not limited in this respect.

In some embodiments, the LO signals may differ in duty cycle (the percentage of one period in which the LO signal is high) and/or offset (the difference between start points of the period). In some embodiments, the LO signals may have an 85% duty cycle and an 80% offset. In some embodiments, each branch of the mixer circuitry (e.g., the in-phase (I) and quadrature phase (Q) path) may operate at an 80% duty cycle, which may result in a significant reduction is power consumption.

The RF input signal 807 (FIG. 8) may comprise a balanced signal, although the scope of the embodiments is not limited in this respect. The I and Q baseband output signals may be provided to low-noise amplifier, such as amplifier circuitry 906 (FIG. 9) or to filter circuitry 908 (FIG. 9).

In some embodiments, the output baseband signals 907 and the input baseband signals 911 may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals 907 and the input baseband signals 911 may be digital baseband signals. In these alternate embodiments, the radio IC circuitry may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry.

In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, or for other spectrums not mentioned here, although the scope of the embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 904 may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 904 may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider. According to some embodiments, the synthesizer circuitry 904 may include digital synthesizer circuitry. An advantage of using a digital synthesizer circuitry is that, although it may still include some analog components, its footprint may be scaled down much more than the footprint of an analog synthesizer circuitry. In some embodiments, frequency input into synthesizer circuitry 904 may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. A divider control input may further be provided by either the baseband processing circuitry 708 a-b (FIG. 7) depending on the desired output frequency 905. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table (e.g., within a Wi-Fi card) based on a channel number and a channel center frequency as determined or indicated by the example application processor 710. The application processor 710 may include, or otherwise be connected to, one of the example security signal converter 101 or the example received signal converter 103 (e.g., depending on which device the example radio architecture is implemented in).

In some embodiments, synthesizer circuitry 904 may be configured to generate a carrier frequency as the output frequency 905, while in other embodiments, the output frequency 905 may be a fraction of the carrier frequency (e.g., one-half the carrier frequency, one-third the carrier frequency). In some embodiments, the output frequency 905 may be a LO frequency (fLO).

FIG. 10 illustrates a functional block diagram of baseband processing circuitry 708 a in accordance with some embodiments. The baseband processing circuitry 708 a is one example of circuitry that may be suitable for use as the baseband processing circuitry 708 a (FIG. 7), although other circuitry configurations may also be suitable. Alternatively, the example of FIG. 10 may be used to implement the example BT baseband processing circuitry 708 b of FIG. 7.

The baseband processing circuitry 708 a may include a receive baseband processor (RX BBP) 1002 for processing receive baseband signals 1009 provided by the radio IC circuitry 706 a-b (FIG. 7) and a transmit baseband processor (TX BBP) 1004 for generating transmit baseband signals 1011 for the radio IC circuitry 706 a-b. The baseband processing circuitry 708 a may also include control logic 1006 for coordinating the operations of the baseband processing circuitry 708 a.

In some embodiments (e.g., when analog baseband signals are exchanged between the baseband processing circuitry 708 a-b and the radio IC circuitry 706 a-b), the baseband processing circuitry 708 a may include ADC 1010 to convert analog baseband signals 1009 received from the radio IC circuitry 706 a-b to digital baseband signals for processing by the RX BBP 1002. In these embodiments, the baseband processing circuitry 708 a may also include DAC 1012 to convert digital baseband signals from the TX BBP 1004 to analog baseband signals 1011.

In some embodiments that communicate OFDM signals or OFDMA signals, such as through baseband processor 708 a, the transmit baseband processor 1004 may be configured to generate OFDM or OFDMA signals as appropriate for transmission by performing an inverse fast Fourier transform (IFFT). The receive baseband processor 1002 may be configured to process received OFDM signals or OFDMA signals by performing an FFT. In some embodiments, the receive baseband processor 1002 may be configured to detect the presence of an OFDM signal or OFDMA signal by performing an autocorrelation, to detect a preamble, such as a short preamble, and by performing a cross-correlation, to detect a long preamble. The preambles may be part of a predetermined frame structure for Wi-Fi communication.

Referring back to FIG. 7, in some embodiments, the antennas 701 (FIG. 7) may each comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result. Antennas 701 may each include a set of phased-array antennas, although embodiments are not so limited.

Although the radio architecture 700A, 700B is illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may comprise one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements may refer to one or more processes operating on one or more processing elements.

The operations and processes described and shown above may be carried out or performed in any suitable order as desired in various implementations. Additionally, in certain implementations, at least a portion of the operations may be carried out in parallel. Furthermore, in certain implementations, less than or more than the operations described may be performed.

The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments. The terms “computing device,” “user device,” “communication station,” “station,” “handheld device,” “mobile device,” “wireless device” and “user equipment” (UE) as used herein refers to a wireless communication device such as a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a femtocell, a high data rate (HDR) subscriber station, an access point, a printer, a point of sale device, an access terminal, or other personal communication system (PCS) device. The device may be either mobile or stationary.

As used within this document, the term “communicate” is intended to include transmitting, or receiving, or both transmitting and receiving. This may be particularly useful in claims when describing the organization of data that is being transmitted by one device and received by another, but only the functionality of one of those devices is required to infringe the claim. Similarly, the bidirectional exchange of data between two devices (both devices transmit and receive during the exchange) may be described as “communicating,” when only the functionality of one of those devices is being claimed. The term “communicating” as used herein with respect to a wireless communication signal includes transmitting the wireless communication signal and/or receiving the wireless communication signal. For example, a wireless communication unit, which is capable of communicating a wireless communication signal, may include a wireless transmitter to transmit the wireless communication signal to at least one other wireless communication unit, and/or a wireless communication receiver to receive the wireless communication signal from at least one other wireless communication unit.

As used herein, unless otherwise specified, the use of the ordinal adjectives “first,” “second,” “third,” etc., to describe a common object, merely indicates that different instances of like objects are being referred to and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

The term “access point” (AP) as used herein may be a fixed station. An access point may also be referred to as an access node, a base station, an evolved node B (eNodeB), or some other similar terminology known in the art. An access terminal may also be called a mobile station, user equipment (UE), a wireless communication device, or some other similar terminology known in the art. Embodiments disclosed herein generally pertain to wireless networks. Some embodiments may relate to wireless networks that operate in accordance with one of the IEEE 802.11 standards.

Some embodiments may be used in conjunction with various devices and systems, for example, a personal computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a personal digital assistant (PDA) device, a handheld PDA device, an on-board device, an off-board device, a hybrid device, a vehicular device, a non-vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless access point (AP), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A/V) device, a wired or wireless network, a wireless area network, a wireless video area network (WVAN), a local area network (LAN), a wireless LAN (WLAN), a personal area network (PAN), a wireless PAN (WPAN), and the like.

Some embodiments may be used in conjunction with one way and/or two-way radio communication systems, cellular radio-telephone communication systems, a mobile phone, a cellular telephone, a wireless telephone, a personal communication system (PCS) device, a PDA device which incorporates a wireless communication device, a mobile or portable global positioning system (GPS) device, a device which incorporates a GPS receiver or transceiver or chip, a device which incorporates an RFID element or chip, a multiple input multiple output (MIMO) transceiver or device, a single input multiple output (SIMO) transceiver or device, a multiple input single output (MISO) transceiver or device, a device having one or more internal antennas and/or external antennas, digital video broadcast (DVB) devices or systems, multi-standard radio devices or systems, a wired or wireless handheld device, e.g., a smartphone, a wireless application protocol (WAP) device, or the like.

Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems following one or more wireless communication protocols, for example, radio frequency (RF), infrared (IR), frequency-division multiplexing (FDM), orthogonal FDM (OFDM), time-division multiplexing (TDM), time-division multiple access (TDMA), extended TDMA (E-TDMA), general packet radio service (GPRS), extended GPRS, code-division multiple access (CDMA), wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, multi-carrier modulation (MDM), discrete multi-tone (DMT), Bluetooth®, global positioning system (GPS), Wi-Fi, Wi-Max, ZigBee, ultra-wideband (UWB), global system for mobile communications (GSM), 2G, 2.5G, 3G, 3.5G, 4G, fifth generation (5G) mobile networks, 3GPP, long term evolution (LTE), LTE advanced, enhanced data rates for GSM Evolution (EDGE), or the like. Other embodiments may be used in various other devices, systems, and/or networks.

The following paragraphs describe examples of various embodiments.

Example 1 includes an apparatus, comprising: interface circuitry; and processor circuitry coupled with the interface circuitry, wherein the processor circuitry is to: encode an ultra-low latency (ULL) packet; and cause transmission of the ULL packet to an Access Point (AP) via the interface circuitry in an unlicensed spectrum, wherein a duration of the ULL packet is less than 20 microseconds.

Example 2 includes the apparatus of Example 1, wherein the ULL packet excludes a legacy preamble of an Institute of Electrical and Electronic Engineers (IEEE) 802.11 packet.

Example 3 includes the apparatus of Example 1 or 2, wherein the processor circuitry is to: cause transmission of the ULL packet to the AP across a wide band.

Example 4 includes the apparatus of any of Examples 1 to 3, wherein the wide band includes an 80 MHz or 160 MHz band.

Example 5 includes the apparatus of any of Examples 1 to 4, wherein a subcarrier frequency spacing for the ULL packet is greater than 312.5 kHz.

Example 6 includes the apparatus of any of Examples 1 to 5, wherein the subcarrier frequency spacing includes 1.25 MHz or 2.5 MHz.

Example 7 includes the apparatus of any of Examples 1 to 6, wherein an Inverse Discrete Fourier Transformation (IDFT)/Discrete Fourier Transformation (DFT) period for the ULL packet includes 0.8 microseconds or 0.4 microseconds.

Example 8 includes the apparatus of any of Examples 1 to 7, wherein a guard interval duration for the ULL packet includes 0.8 microseconds or 0.4 microseconds.

Example 9 includes the apparatus of any of Examples 1 to 8, wherein an Orthogonal Frequency Division Multiplexing (OFDM) symbol duration for the ULL packet is less than 3.2 microseconds.

Example 10 includes the apparatus of any of Examples 1 to 9, wherein the OFDM symbol duration includes 1.6 microseconds or 0.8 microseconds.

Example 11 includes the apparatus of any of Examples 1 to 10, wherein a duration of a short-training field for the ULL packet is less than 4 microseconds.

Example 12 includes the apparatus of any of Examples 1 to 11, wherein the duration of the short-training field includes 2 microseconds or 1 microsecond.

Example 13 includes the apparatus of any of Examples 1 to 12, wherein a duration of a long-training field for the ULL packet is less than 4 microseconds.

Example 14 includes the apparatus of any of Examples 1 to 13, wherein the duration of the long-training field includes 2.4 microseconds or 1.2 microsecond.

Example 15 includes the apparatus of any of Examples 1 to 14, wherein a signal field for the ULL packet includes 2 Orthogonal Frequency Division Multiplexing (OFDM) symbols.

Example 16 includes the apparatus of any of Examples 1 to 15, wherein a duration of a preamble of the ULL packet is less than a duration of a legacy preamble of an Institute of Electrical and Electronic Engineers (IEEE) 802.11 packet.

Example 17 includes the apparatus of any of Examples 1 to 16, wherein the duration of the preamble of the ULL packet includes 7.6 microseconds or 3.8 microsecond.

Example 18 includes the apparatus of any of Examples 1 to 17, wherein the processor circuitry is to: encode the ULL packet with dual-carrier modulation or quad-carrier modulation.

Example 19 includes the apparatus of any of Examples 1 to 18, wherein the processor circuitry is to: cause transmission of the ULL packet to the AP when there is an ongoing transmission from an Overlapping Basic Service Set (OBSS) network.

Example 20 includes the apparatus of any of Examples 1 to 19, wherein the processor circuitry is to identify the ULL packet via: a higher layer packet classification tag; a Media Access Control (MAC) layer traffic flow identifier (ID); or a dedicated traffic identifier (TID).

Example 21 includes the apparatus of any of Examples 1 to 20, wherein the processor circuitry is to: cause transmission of the ULL packet to the AP over 6 GHz band.

Example 22 includes the apparatus of any of Examples 1 to 21, wherein the processor circuitry is to: encode the ULL packet with 64 tones or 128 tones.

Example 23 includes the apparatus of any of Examples 1 to 22, wherein a size of the ULL packet is equal to or less than a predefined packet size threshold.

Example 24 includes the apparatus of any of Examples 1 to 23, wherein a duration of the ULL packet is equal to or less than a predefined packet duration threshold.

Example 25 includes a method, comprising: encoding an ultra-low latency (ULL) packet; and transmitting the ULL packet to an Access Point (AP) in an unlicensed spectrum, wherein a duration of the ULL packet is less than 20 microseconds.

Example 26 includes the method of Example 25, wherein the ULL packet excludes a legacy preamble of an Institute of Electrical and Electronic Engineers (IEEE) 802.11 packet.

Example 27 includes the method of Example 25 or 26, further comprising: transmitting the ULL packet to the AP across a wide band.

Example 28 includes the method of any of Examples 25 to 27, wherein the wide band includes an 80 MHz or 160 MHz band.

Example 29 includes the method of any of Examples 25 to 28, wherein a subcarrier frequency spacing for the ULL packet is greater than 312.5 kHz.

Example 30 includes the method of any of Examples 25 to 29, wherein the subcarrier frequency spacing includes 1.25 MHz or 2.5 MHz.

Example 31 includes the method of any of Examples 25 to 30, wherein an Inverse Discrete Fourier Transformation (IDFT)/Discrete Fourier Transformation (DFT) period for the ULL packet includes 0.8 microseconds or 0.4 microseconds.

Example 32 includes the method of any of Examples 25 to 31, wherein a guard interval duration for the ULL packet includes 0.8 microseconds or 0.4 microseconds.

Example 33 includes the method of any of Examples 25 to 32, wherein an Orthogonal Frequency Division Multiplexing (OFDM) symbol duration for the ULL packet is less than 3.2 microseconds.

Example 34 includes the method of any of Examples 25 to 33, wherein the OFDM symbol duration includes 1.6 microseconds or 0.8 microseconds.

Example 35 includes the method of any of Examples 25 to 34, wherein a duration of a short-training field for the ULL packet is less than 4 microseconds.

Example 36 includes the method of any of Examples 25 to 35, wherein the duration of the short-training field includes 2 microseconds or 1 microsecond.

Example 37 includes the method of any of Examples 25 to 36, wherein a duration of a long-training field for the ULL packet is less than 4 microseconds.

Example 38 includes the method of any of Examples 25 to 37, wherein the duration of the long-training field includes 2.4 microseconds or 1.2 microsecond.

Example 39 includes the method of any of Examples 25 to 38, wherein a signal field for the ULL packet includes 2 Orthogonal Frequency Division Multiplexing (OFDM) symbols.

Example 40 includes the method of any of Examples 25 to 39, wherein a duration of a preamble of the ULL packet is less than a duration of a legacy preamble of an Institute of Electrical and Electronic Engineers (IEEE) 802.11 packet.

Example 41 includes the method of any of Examples 25 to 40, wherein the duration of the preamble of the ULL packet includes 7.6 microseconds or 3.8 microsecond.

Example 42 includes the method of any of Examples 25 to 41, further comprising: encoding the ULL packet with dual-carrier modulation or quad-carrier modulation.

Example 43 includes the method of any of Examples 25 to 42, further comprising: transmitting the ULL packet to the AP when there is an ongoing transmission from an Overlapping Basic Service Set (OBSS) network.

Example 44 includes the method of any of Examples 25 to 43, further comprising identifying the ULL packet via: a higher layer packet classification tag; a Media Access Control (MAC) layer traffic flow identifier (ID); or a dedicated traffic identifier (TID).

Example 45 includes the method of any of Examples 25 to 44, further comprising: transmitting the ULL packet to the AP over 6 GHz band.

Example 46 includes the method of any of Examples 25 to 45, further comprising: encoding the ULL packet with 64 tones or 128 tones.

Example 47 includes the method of any of Examples 25 to 46, wherein a size of the ULL packet is equal to or less than a predefined packet size threshold.

Example 48 includes the method of any of Examples 25 to 47, wherein a duration of the ULL packet is equal to or less than a predefined packet duration threshold.

Example 49 includes an apparatus, comprising: means for encoding an ultra-low latency (ULL) packet; and means for transmitting the ULL packet to an Access Point (AP) in an unlicensed spectrum, wherein a duration of the ULL packet is less than 20 microseconds.

Example 50 includes the apparatus of Example 49, wherein the ULL packet excludes a legacy preamble of an Institute of Electrical and Electronic Engineers (IEEE) 802.11 packet.

Example 51 includes the apparatus of Example 49 or 50, further comprising: means for transmitting the ULL packet to the AP across a wide band.

Example 52 includes the apparatus of any of Examples 49 to 51, wherein the wide band includes an 80 MHz or 160 MHz band.

Example 53 includes the apparatus of any of Examples 49 to 52, wherein a subcarrier frequency spacing for the ULL packet is greater than 312.5 kHz.

Example 54 includes the apparatus of any of Examples 49 to 53, wherein the subcarrier frequency spacing includes 1.25 MHz or 2.5 MHz.

Example 55 includes the apparatus of any of Examples 49 to 54, wherein an Inverse Discrete Fourier Transformation (IDFT)/Discrete Fourier Transformation (DFT) period for the ULL packet includes 0.8 microseconds or 0.4 microseconds.

Example 56 includes the apparatus of any of Examples 49 to 55, wherein a guard interval duration for the ULL packet includes 0.8 microseconds or 0.4 microseconds.

Example 57 includes the apparatus of any of Examples 49 to 56, wherein an Orthogonal Frequency Division Multiplexing (OFDM) symbol duration for the ULL packet is less than 3.2 microseconds.

Example 58 includes the apparatus of any of Examples 49 to 57, wherein the OFDM symbol duration includes 1.6 microseconds or 0.8 microseconds.

Example 59 includes the apparatus of any of Examples 49 to 58, wherein a duration of a short-training field for the ULL packet is less than 4 microseconds.

Example 60 includes the apparatus of any of Examples 49 to 59, wherein the duration of the short-training field includes 2 microseconds or 1 microsecond.

Example 61 includes the apparatus of any of Examples 49 to 60, wherein a duration of a long-training field for the ULL packet is less than 4 microseconds.

Example 62 includes the apparatus of any of Examples 49 to 61, wherein the duration of the long-training field includes 2.4 microseconds or 1.2 microsecond.

Example 63 includes the apparatus of any of Examples 49 to 62, wherein a signal field for the ULL packet includes 2 Orthogonal Frequency Division Multiplexing (OFDM) symbols.

Example 64 includes the apparatus of any of Examples 49 to 63, wherein a duration of a preamble of the ULL packet is less than a duration of a legacy preamble of an Institute of Electrical and Electronic Engineers (IEEE) 802.11 packet.

Example 65 includes the apparatus of any of Examples 49 to 64, wherein the duration of the preamble of the ULL packet includes 7.6 microseconds or 3.8 microsecond.

Example 66 includes the apparatus of any of Examples 49 to 65, further comprising: means for encoding the ULL packet with dual-carrier modulation or quad-carrier modulation.

Example 67 includes the apparatus of any of Examples 49 to 66, further comprising: means for transmitting the ULL packet to the AP when there is an ongoing transmission from an Overlapping Basic Service Set (OBSS) network.

Example 68 includes the apparatus of any of Examples 49 to 67, further comprising means for identifying the ULL packet via: a higher layer packet classification tag; a Media Access Control (MAC) layer traffic flow identifier (ID); or a dedicated traffic identifier (TID).

Example 69 includes the apparatus of any of Examples 49 to 68, further comprising: means for transmitting the ULL packet to the AP over 6 GHz band.

Example 70 includes the apparatus of any of Examples 49 to 69, further comprising: means for encoding the ULL packet with 64 tones or 128 tones.

Example 71 includes the apparatus of any of Examples 49 to 70, wherein a size of the ULL packet is equal to or less than a predefined packet size threshold.

Example 72 includes the apparatus of any of Examples 49 to 71, wherein a duration of the ULL packet is equal to or less than a predefined packet duration threshold.

Example 73 includes a computer-readable medium having instructions stored thereon, the instructions when executed by processor circuitry cause the processor circuitry to perform the method of any of Examples 25 to 48.

Example 74 includes a Wireless Fidelity (Wi-Fi) device as shown and described in the description.

Example 75 includes a method performed at a Wireless Fidelity (Wi-Fi) device as shown and described in the description.

Example 76 includes a Station (STA) as shown and described in the description.

Example 77 includes a method performed at a Station (STA) as shown and described in the description.

Example 78 includes an Access Point (AP) as shown and described in the description.

Example 79 includes a method performed at an Access Point (AP) as shown and described in the description.

Although certain embodiments have been illustrated and described herein for purposes of description, a wide variety of alternate and/or equivalent embodiments or implementations calculated to achieve the same purposes may be substituted for the embodiments shown and described without departing from the scope of the disclosure. This application is intended to cover any adaptations or variations of the embodiments discussed herein. Therefore, it is manifestly intended that embodiments described herein be limited only by the appended claims and the equivalents thereof. 

What is claimed is:
 1. An apparatus, comprising: interface circuitry; and processor circuitry coupled with the interface circuitry, wherein the processor circuitry is to: encode an ultra-low latency (ULL) packet; and cause transmission of the ULL packet to an Access Point (AP) via the interface circuitry in an unlicensed spectrum, wherein a duration of the ULL packet is less than 20 microseconds.
 2. The apparatus of claim 1, wherein the ULL packet excludes a legacy preamble of an Institute of Electrical and Electronic Engineers (IEEE) 802.11 packet.
 3. The apparatus of claim 1, wherein the processor circuitry is to: cause transmission of the ULL packet to the AP across a wide band.
 4. The apparatus of claim 3, wherein the wide band includes an 80 MHz or 160 MHz band.
 5. The apparatus of claim 1, wherein a subcarrier frequency spacing for the ULL packet is greater than 312.5 kHz.
 6. The apparatus of claim 5, wherein the subcarrier frequency spacing includes 1.25 MHz or 2.5 MHz.
 7. The apparatus of claim 1, wherein an Inverse Discrete Fourier Transformation (IDFT)/Discrete Fourier Transformation (DFT) period for the ULL packet includes 0.8 microseconds or 0.4 microseconds.
 8. The apparatus of claim 1, wherein a guard interval duration for the ULL packet includes 0.8 microseconds or 0.4 microseconds.
 9. The apparatus of claim 1, wherein an Orthogonal Frequency Division Multiplexing (OFDM) symbol duration for the ULL packet is less than 3.2 microseconds.
 10. The apparatus of claim 9, wherein the OFDM symbol duration includes 1.6 microseconds or 0.8 microseconds.
 11. The apparatus of claim 1, wherein a duration of a short-training field for the ULL packet is less than 4 microseconds.
 12. The apparatus of claim 11, wherein the duration of the short-training field includes 2 microseconds or 1 microsecond.
 13. The apparatus of claim 1, wherein a duration of a long-training field for the ULL packet is less than 4 microseconds.
 14. The apparatus of claim 13, wherein the duration of the long-training field includes 2.4 microseconds or 1.2 microsecond.
 15. The apparatus of claim 1, wherein a signal field for the ULL packet includes 2 Orthogonal Frequency Division Multiplexing (OFDM) symbols.
 16. The apparatus of claim 1, wherein a duration of a preamble of the ULL packet is less than a duration of a legacy preamble of an Institute of Electrical and Electronic Engineers (IEEE) 802.11 packet.
 17. The apparatus of claim 16, wherein the duration of the preamble of the ULL packet includes 7.6 microseconds or 3.8 microsecond.
 18. The apparatus of claim 1, wherein the processor circuitry is to: encode the ULL packet with dual-carrier modulation or quad-carrier modulation.
 19. The apparatus of claim 1, wherein the processor circuitry is to: cause transmission of the ULL packet to the AP when there is an ongoing transmission from an Overlapping Basic Service Set (OBSS) network.
 20. The apparatus of claim 1, wherein the processor circuitry is to identify the ULL packet via: a higher layer packet classification tag; a Media Access Control (MAC) layer traffic flow identifier (ID); or a dedicated traffic identifier (TID).
 21. The apparatus of claim 1, wherein the processor circuitry is to: cause transmission of the ULL packet to the AP over 6 GHz band.
 22. The apparatus of claim 1, wherein the processor circuitry is to: encode the ULL packet with 64 tones or 128 tones.
 23. The apparatus of claim 1, wherein a size of the ULL packet is equal to or less than a predefined packet size threshold.
 24. The apparatus of claim 1, wherein a duration of the ULL packet is equal to or less than a predefined packet duration threshold. 